-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLDR-18267 BRS v47: update logKnownIssues #4322
CLDR-18267 BRS v47: update logKnownIssues #4322
Conversation
remaining bugs… |
3119dfd
to
94183a1
Compare
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Updated tests to point to the updated tickets: - CLDR-15663 to CLDR-17857 - CLDR-17756 to CLDR-17945 - CLDR-17544 to CLDR-17849
94183a1
to
2cc8da8
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
sorry, i had garbage in the commit message… copy and paste err |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I wonder if we should update anything in our ticket handling process so that we don't have to update known issue ticket numbers across releases? Maybe resolve in subtasks if we expect the work to stretch across more than one release?
yeah, logKnownIssues predates subtasks — that's might be a good idea to say, always make a subtask for the logKnownIssue. Makes it easier to kick the can down the road- but stops taking time trying to track down this issue. |
CLDR-18267
Three tickets were already closed but needed the logKnownIssues adjusted:
CLDR-15663 to CLDR-17857
CLDR-17756 to CLDR-17945
CLDR-17544 to CLDR-17849
This PR completes the ticket.
ALLOW_MANY_COMMITS=true